IuGW architecture

ABSTRACT

Systems and methods are disclosed for a 3G gateway. In one embodiment, a system is disclosed, comprising a gateway situated between a 3G radio access network (RAN) and a core network, the gateway providing resource management for a nodeB, and providing routing and node management for another base station, wherein the base station may be configured to provide, as a virtual RNC, radio resource control, power control, ciphering, and multiplexing of multiple users onto a transmission path for a first mobile device attached to the nodeB; the gateway may be configured to relay traffic for a second mobile device attached to the base station; and the gateway may be configured to relay traffic to the core network from both the nodeB and the base station via an IuCS interface and an IuPS interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119(e) to U.S.Provisional Pat. App. No. 62/310,173, “IuGW Architecture,” filed Mar.18, 2016, which is also hereby incorporated by reference in its entiretyfor all purposes. This application also hereby incorporates by referenceU.S. Pat. No. 8,879,416, “Heterogeneous Mesh Network and Multi-RAT NodeUsed Therein,” filed May 8, 2013; U.S. Pat. No. 9,113,352,“Heterogeneous Self-Organizing Network for Access and Backhaul,” filedSep. 12, 2013; U.S. Pat. No. 8,867,418, “Methods of Incorporating an AdHoc Cellular Network Into a Fixed Cellular Network,” filed Feb. 18,2014; U.S. patent application Ser. No. 14/034,915, “Dynamic Multi-AccessWireless Network Virtualization,” filed Sep. 24, 2013; U.S. patentapplication Ser. No. 14/289,821, “Method of Connecting Security Gatewayto Mesh Network,” filed May 29, 2014; U.S. patent application Ser. No.14/500,989, “Adjusting Transmit Power Across a Network,” filed Sep. 29,2014; U.S. patent application Ser. No. 14/506,587, “Multicast andBroadcast Services Over a Mesh Network,” filed Oct. 3, 2014; U.S. patentapplication Ser. No. 14/510,074, “Parameter Optimization and EventPrediction Based on Cell Heuristics,” filed Oct. 8, 2014, U.S. patentapplication Ser. No. 14/642,544, “Federated X2 Gateway,” filed Mar. 9,2015, and U.S. patent application Ser. No. 14/936,267, “Self-Calibratingand Self-Adjusting Network,” filed Nov. 9, 2015, each in its entiretyfor all purposes. This document also hereby incorporates by referenceU.S. Pat. Nos. 9,107,092, 8,867,418, and 923547 in their entirety. Thisdocument also hereby incorporates by reference U.S. patent applicationSer. No. 14/822,839 in its entirety.

BACKGROUND

The Universal Mobile Telecommunications System (UMTS) is a thirdgeneration (3G) mobile cellular system for networks based on the GSMstandard. Developed and maintained by the 3GPP (3rd GenerationPartnership Project), UMTS is a component of the InternationalTelecommunications Union IMT-2000 standard set and compares with theCDMA2000 standard set for networks based on the competing 3G cdmaOnetechnology. UMTS uses wideband code division multiple access (W-CDMA)radio access technology (RAT) to offer greater spectral efficiency andbandwidth to mobile network operators. UMTS uses an interface called Iubbetween the cellular base station and the radio network controller (RNC)in the core network, which enables the RNC to perform the majority ofrequired functions, and for the cellular base station, or nodeB, toperform primarily radio transceive, baseband and analog-digitalconversion functions.

A femtocell is a small, low-power cellular base station, typicallydesigned for use in a home or small business. A broader term which ismore widespread in the industry is small cell, with femtocell as asubset. A femtocell may connect to the service provider's network viabroadband (such as DSL or cable); typical designs support four to eightsimultaneously active mobile phones in a residential setting dependingon version number and femtocell hardware, and eight to 16 mobile phonesin enterprise settings. A femtocell allows service providers to extendservice coverage indoors or at the cell edge, especially where accesswould otherwise be limited or unavailable. Although much attention isfocused on WCDMA, the concept is applicable to all standards, includingGSM, CDMA2000, TD-SCDMA, WiMAX and LTE solutions.

The key interface in femtocell architectures is that between thefemtocells and the femtocell gateway. Standardisation enables a widerchoice of femtocell products to be used with any gateway, increasingcompetitive pressure and driving costs down. For the common WCDMAfemtocells, this is defined as the Iuh interface. In the Iuharchitecture, the femtocell gateway sits between the femtocell and thecore network and performs the necessary translations to ensure thefemtocells appear as a radio network controller (RNC) to existing mobileswitching centres (MSCs). Each femtocell talks to the femtocell gatewayand femtocell gateways talk to the Core Network Elements (CNE) (MSC forcircuit-switched calls, SGSN for packet-switched calls).

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1A and 1B are network architecture diagrams for prior art 3GPP 3Gnetworks.

FIG. 2 is a schematic network architecture diagram for 3G and other-Gprior art networks.

FIG. 3 is a schematic network architecture in accordance with someembodiments.

FIG. 4 is a schematic network architecture in accordance with somefurther embodiments.

FIG. 5 is a schematic network architecture showing security andsignaling characteristics in accordance with some embodiments.

FIG. 6 is a schematic network architecture showing base station groupingin accordance with some embodiments.

FIG. 7 is a schematic base station deployment topology diagram, inaccordance with some embodiments.

FIG. 8 is a signaling call flow showing a handover of a circuit-switchedsession at a gateway, in accordance with some embodiments.

FIG. 9 is a signaling call flow showing a handover of a packet-switchedsession at a gateway, in accordance with some embodiments.

FIG. 10 is a signaling call flow showing a two-phase macro to rural zonemobility scenario, in accordance with some embodiments.

FIG. 11 is a signaling call flow showing an Iuh anchored rural to ruralzone mobility scenario, in accordance with some embodiments.

FIG. 12 is a signaling call flow showing additional aspects of a ruralto rural zone mobility scenario, in accordance with some embodiments.

FIG. 13 is a signaling call flow showing base station registration, inaccordance with some embodiments.

FIG. 14 is a schematic architecture diagram of an exemplary base stationtogether with an exemplary gateway, in accordance with some embodiments.

FIG. 15 is a signaling call flow showing handin with call connectmessage forking, in accordance with some embodiments.

FIG. 16 is a schematic network architecture diagram showing RTPlocalization, in accordance with some embodiments.

FIG. 17 is a schematic architecture diagram of an exemplary gateway, inaccordance with some embodiments.

FIG. 18 is a schematic architecture diagram of an exemplary basestation, in accordance with some embodiments.

SUMMARY

Systems and methods are disclosed for a 3G gateway. In one embodiment, asystem is disclosed, comprising a base station management gatewaysituated between a 3G radio access network (RAN) and a core network, thebase station management gateway providing resource management for anodeB and the base station management gateway providing routing and nodemanagement for a base station, wherein the base station may beconfigured to provide radio resource control, power control, ciphering,and multiplexing of multiple users onto a transmission path for a firstmobile device attached to the nodeB; the base station management gatewaymay be configured to relay traffic for a second mobile device attachedto the base station; and the base station management gateway may beconfigured to relay traffic to the core network from both the nodeB andthe base station via an IuCS interface and an IuPS interface.

The base station management gateway may be configured to interact withthe 3G RAN as a Radio Network Controller (RNC) and with the base stationas a home nodeB gateway (HNBGW). The base station management gateway maybe configured to receive packets from the nodeB and the base station,and to direct the received packets to either an IuCS interface towardthe core network or an IuPS core network interface toward the corenetwork. The base station management gateway may be configured to use anodeB application part (NBAP) protocol, an access link controlapplication protocol (ALCAP) protocol, a radio access networkapplication part (RANAP) protocol, and a radio network subsystemapplication part (RNSAP) protocol. The base station management gatewaymay be configured to receive Iub protocol messages from a 3G basestation and Iuh protocol messages from a home nodeB. The base stationmanagement gateway may be configured to terminate an encryptedconnection with a 3G mobile device, thereby providing a secure anchorpoint for the 3G mobile device for connection to the core network.

The base station management gateway may be configured to terminateencrypted tunnels from the core network, from the first mobile deviceand second mobile device, and from the base station, and wherein thebase station may be a home nodeB, and wherein the encrypted tunnels maybe Internet Protocol security (IPsec) or General Packet Radio ServiceTunneling Protocol (GTP) tunnels. The base station management gatewaymay be configured to coordinate with a second base station managementgateway using an Iur protocol. The base station management gateway maybe configured to be aggregated with a second base station managementgateway via an interposing Iur protocol gateway. The base stationmanagement gateway may be a virtualization gateway providingvirtualization of a plurality of home nodeBs toward the core network.The base station management gateway may be configured to suppress pagingmessages for managed base stations. The base station management gatewaymay be configured to perform inter-radio access technology steering of asession from a first radio access technology (RAT) to a second RAT, thefirst RAT being one of 2G, 3G, 4G, and wireless local area networking(WLAN). The base station management gateway may be configured to provideone or more application-aware inter-radio access technology (inter-RAT)slices across 3G, 4G, and wireless local area networking (WLAN)technologies, the inter-RAT slices being based on application-layerinformation gathered at the base station management gateway. The basestation management gateway may be configured to present itself towardthe core network as a virtual radio network controller (VRNC). The corenetwork may be a 3G Universal Mobile Telecommunications System (UMTS)core network comprising a mobile switching center (MSC) and a servinggeneral packet radio service support node (SGSN). The base stationmanagement gateway may be configured to provide handovers between thenodeB and the base station using an Iub interface with the nodeB and anIuh interface, an Iur interface, an Iurh interface, or an S1 interfacewith the base station. The base station may be a multi-radio accessnetwork (multi-RAT) base station providing two or more of 2G, 3G, 4G,and wireless local area network (wireless LAN) radio accesstechnologies. The base station management gateway may be configured toprovide handovers between the nodeB and one or more of a 2G basestation, a 4G base station, and a Wi-Fi access point.

Systems and methods are also disclosed for grouping base stations. Inone embodiment, a method is disclosed, comprising: receiving, at agateway, the gateway positioned between a core network and a radioaccess network, a configuration information request from a base station;analyzing, at the gateway, a topology of a radio access network, theradio access network including the base station; grouping, at thegateway, the base station into a first group based on the topology;sending, from the gateway to the base station, a grouping messageindicating that the base station may be placed in the first group; andterminating connections from the core network to one or more basestations in the first group at the gateway as a back-to-back proxy,thereby hiding the topology of the radio access network from the corenetwork.

The core network may include a radio network controller (RNC) or aplurality of RNCs. The core network may include a System ArchitectureEvolution (SAE) core network or a Long Term Evolution (LTE) corenetwork, and may further comprise interworking of communications fromthe base station to the core network via an S2a or S2b protocol.Analyzing the topology may include determining adjacent base stations ofthe base station. Analyzing the topology may include using latitude andlongitude location data of the base station. Analyzing the topology mayinclude using latitude and longitude location data of the base stationusing a global positioning system (GPS) receiver. The base station maybe a home nodeB hidden from a core network, and wherein the adjacentbase stations may be nodeBs visible to the core network. Grouping mayinclude determining a second group of base stations, the first group ofbase stations each coupled to a core network via a point to point Iuprotocol connection terminating at the core network, the second group ofbase stations each coupled to a core network via a point to point Iuprotocol connection terminating at the gateway. The method may includeperforming a user equipment (UE) handover from the first group of basestations to the second group of base stations. The method may includeperforming a user equipment (UE) handover from the second group of basestations to the first group of base stations. The method may includeallocating a location area code (LAC), a service area code (SAC), and arouting area code (RAC) to the base station. The method may includeallocating a location area code (LAC), a service area code (SAC), and arouting area code (RAC) to the base station from a pool of LACs, SACs,or RACs. The method may include reallocating a location area code (LAC),a service area code (SAC), or a routing area code (RAC) from the basestation to another base station in the first group. The method mayinclude proxying, at the gateway, one or more interfaces for presentingthe first group as a single base station toward the core network. Themethod may include proxying, at the gateway, one or more interfaces forpresenting the first group as a virtual radio access network (vRAN)toward the core network. The method may include proxying, at thegateway, one or more interfaces for presenting the first group as asingle umbrella cell toward the core network.

Systems and methods are also disclosed for RTP localization. In oneembodiment, a method is disclosed, comprising: detecting, at a gateway,a packet-based voice session with a source base station and a targetbase station, the source base station being attached to an originatinguser equipment and the target base station being attached to aterminating user equipment, the source base station and the target basestation each being coupled to a core network via the gateway;performing, at the gateway, endpoint lookup of the terminating userequipment; and redirecting, via the gateway, call audio of thepacket-based voice session to the terminating user equipment from apathway through the core network to a pathway through the gateway.

The source base station and the target base station may be a single basestation and the packet-based voice session may be terminated at thesource base station. The packet-based voice session may be a real timeprotocol (RTP) voice session. The packet-based voice session may becircuit-switched or packet-switched. The packet-based voice session maybe routed using hairpin routing. The packet-based voice session may be acircuit-switched fallback (CSFB) call. The method may include performingendpoint lookup using a phone number of the terminating user equipment.The method may include redirecting the call audio of the packet-basedvoice session within a group of base stations or across multiple groupsof base stations, wherein the group of base stations or multiple groupsof base stations may be managed by the gateway. The method may includeredirecting the call audio of the packet-based voice session from a 2Gor 4G base station to a 3G base station. The method may includeredirecting the call audio of the packet-based voice session from a 2Gor 3G base station to a 4G base station. The method may includeproviding, at the gateway, three-way calling, call hold, callconferencing, or improved voice quality for the packet-based voicesession. The method may include reducing bandwidth required on a linkbetween the gateway and the core network.

DETAILED DESCRIPTION

Overview

Through its HetNet Gateway (HNG)™, the Parallel Wireless solution canorchestrate and manage the Radio Access Network (RAN) across multipletechnologies, including 3G, 4G and Wi-Fi, with high ease of use. Thecenterpiece of the Parallel Wireless solution is the HetNet Gateway,which is the wireless industry's first carrier-grade, high-performanceRAN orchestrator that is based on software-defined networking (SDN) andnetwork functions virtualization (NFV), and is 100 percent compliantwith all open and standard interfaces as defined by the 3rd GenerationPartnership Project (3GPP). The Parallel Wireless HNG virtualizes theRAN interfaces to manage the 4G and 3G (Long Term Evolution, or LTE, anduniversal mobile telecommunications system, or UMTS) RANs(HomeNodeBs/NodeBs and eNodeBs/HeNodeBs) in real-time viamulti-technology self-organizing network (SON) and gateway functionalitywhile abstracting RAN changes from the core network and the core networkitself from the RAN. The Parallel Wireless HNG virtualizes thousands ofbase stations to look like a smaller number of virtualized “boomercells” to the core. The Parallel Wireless HNG also virtualizes radionetwork nodes such as Wi-Fi access points (APs), eNodeBs and NodeBs andmakes them self-configurable, self-adjustable, and self-healing, helpingwith initial installation and ongoing maintenance. The Parallel WirelessHNG acts like a virtual radio network controller (vRNC or virtual RNC)for multi-RAT network handling resources for different technologies 3G,LTE/4G and WiFi while optimizing call processing towards radio and corenetwork elements such as the mobile switching center (MSC), servingglobal packet radio system (GPRS) support node (SGSN), gateway GPRSsupport node (GGSN), evolved packet core (EPC) for 4G, home subscriberserver (HSS), and policy charging and rules function (PCRF).

Paired with the Parallel Wireless HNG, the Parallel Wireless basestation, the Converged Wireless System (CWS)™, is a multi-RAT basestation with LTE, Wi-Fi, and 3G technologies that provides a flexibleoutdoor and in-vehicle solution in conjunction with the ParallelWireless HNG. The combined system is a cloud-based network orchestrationsystem that maximizes virtualization, and functions in a 3GPPstandards-based Heterogeneous Network (HetNet) to bring 3G, Wi-Fi and 4Goperators better technology at lower cost. The Parallel Wirelesssolution addresses key challenges in delivering 3G/4G coverage,capacity, and quality of service (QoS), regardless of the cell size,e.g., femtocell, pico cell, micro cell, metro cell, or macro cell. TheParallel Wireless solution is also easy to deploy with automatedconfiguration and ongoing optimization.

This disclosure covers a 3G vRNC/HNBGW solution provided by the ParallelWireless HNG. This disclosure also captures architecture and call flowdetails for an IuGw feature. The proposed IuGw sits in between a basestation, such as the Parallel Wireless CWS (which acts as an HNB), and acore network, which may include an external HNBGW on the Iuh interface.To the CWS (HNB) the IuGW acts as and virtualizes an HNBGW, and to HNBGWit acts as a virtual HNB. The system is generalizable to provideinteroperability among any-G RAN access nodes with various combinationsof core networks, including with a combined 3G and a 4G core network.

Architecture with an IuGw Plus Iub Over IP to MSC.

Using the architecture described herein, it is possible to enable 3Gpacket and circuit calling and data over IP with a flexible and scalablearchitecture. A gateway, called variously the Parallel Wireless HNG orParallel Wireless HNG, acts as a 3G radio network controller (RNC) andprovides one or more virtualized nodeBs as needed using grouping andmapping. It interfaces with an existing MSC, SGSN via IuCS, IuPS, insome embodiments. The advantages of this architecture include thehelpful features of virtualized cells, here, virtual nodeBs, as with theParallel Wireless LTE virtualization scheme. Also, significantly, usingthis architecture it is possible to provide an all-IP RAN, with fewerlegacy interfaces provided at the core network. This architecture may beadapted for various use cases: emergency services, Band 14 services,multi-operator core networks (MOCN). Iu-Flex can be used for 3G MOCN ormulti-MSC, or to provide resiliency across data centers.

As compared to the use of femto cells in an existing network, CWS isvery different from femto in scale, RF power/coverage area andcapabilities; femto needs external AAA but this architecture does not;femto capacity is additive on top of current network, as opposed to noadditional cost with Parallel Wireless HNG; with Parallel Wireless HNGconnecting to MSC/SGSN it can provide better 911/LBS solution;simplified network architecture at low cost/Cleaner integration; andthis CWS/Parallel Wireless HNG solution is not a femto solution hencedoes not need femto GW. The CWS solution is ideal for a greenfieldscenario, providing both 3G and 4G connectivity, in conjunction with theParallel Wireless HetNet Gateway. However, the CWS and HNG may also beleveraged to provide effective brownfield network architectures. Inother words, in a greenfield scenario, it is possible to convert any-Gto proprietary Iuh.

The following references are incorporated by reference in theirentirety: UTRAN Overall Description—3GPP TS 25.401 V8.2.0 (2008-12) [1];UTRAN Architecture for 3G Home Node B—3GPP TS 25.467 V.8.10 (2009-03)[2]; 3GPP TS 29.281 GPRS Tunneling Protocols—User Plane (GTP-U) [3];3GPP TS 29.060 GPRS Tunneling Protocol [4]; 3GPP TS 25.413 RANAPSignalling [5]; 3GPP TS 23.003 Numbering, Addressing and Identification[6]; 3GPP TS 25.468—UTRAN Iuh Interface RANAP User Adaption (RUA)Signaling [7]; 3GPP TS 25.469—UTRAN Iuh Interface RANAP User Adaption(HNBAP) Signaling [8].

FIGS. 1A and 1B are network architecture diagrams for prior art 3GPP 3Gnetworks. FIG. 1A shows a 3GPP UTRAN architecture. FIG. 1B shows a 3GPPHome NodeB (femto) architecture. As shown in FIG. 1A, the 3GPP UTRANarchitecture includes a mobile station 101, a nodeB 102 (also known as abase transceiver station or BTS), a radio network controller (RNC) 103,and a mobile core 106, the mobile core including a serving GPRS supportnode (SGSN) 104 and a mobile switching center (MSC) 105. The RNCperforms functions that include radio resource control, assigningscrambling codes to UEs, power control, ciphering, Kasumi (UE to RNC;note that nodeB connection is not assumed to be secure), and otherfunctions. The MSC acts as a telephone exchange that makes theconnection between mobile users within the network, from mobile users tothe public switched telephone network and from mobile users to othermobile networks. The MSC also administers handovers to neighbouring basestations, keeps a record of the location of the mobile subscribers, isresponsible for subscriber services and billing. The Serving GPRSSupport Node (SGSN) is a main component of the GPRS network, whichhandles all packet switched data within the network, e.g. the mobilitymanagement and authentication of the users. The SGSN performs the samefunctions as the MSC for voice traffic. Between the MS 101 and nodeB 102is a Uu air interface, between the nodeB and the RNC is an Iubinterface, and between the RNC and the core are two interfaces, IuPS andIuCS. IuPS is the interface used for packet-switched connections. IuCSis the interface used for circuit-switched connections, which in 3Ginclude phone calls.

FIG. 1B shows a 3GPP femto architecture, which is similar to FIG. 1A.This architecture includes a mobile station 111, a nodeB 112 (also knownas a base transceiver station or BTS), a radio network controller (RNC)113, and a mobile core 116, the mobile core including a serving GPRSsupport node (SGSN) 114 and a mobile switching center (MSC) 115. Whilethe Uu interface is unchanged, the interface between the BTS and RNC isIuh instead of Iub, and also includes an IPsec tunnel between the nodes.The Iub interface is an interface and protocol that allows a macro basestation to control the majority of the functions of a nodeB, exceptbaseband and analog-digital conversion. Iub includes control mechanismsto allow an RNC to directly control a NodeB to do all of the following:resource management; scheduling; encryption/decryption; power control;etc. In 3GPP, a regular nodeB does not perform encryption. Iub can beused over IP transport. Iuh is a more lightweight protocol allowing for,e.g., radio resource management at a HNB or femto cell itself. While itis useful to enable a base station to But for carriers with existingmacros deployed, it does not make sense to switch already-deployed macrobase stations using Iub to Home nodeBs using Iuh; as well, macro basestations have coverage advantages. However, the two interfaces aresimilar because both Iub and Iuh terminate at a RNC.

FIG. 2 is a schematic network architecture diagram for 3G and other-Gprior art networks. The diagram shows a plurality of “Gs,” including 2G,3G, 4G, and Wi-Fi. 2G is represented by GERAN 201, which includes a 2Gdevice 201 a, BTS 201 b, and BSC 201 c. 3G is represented by UTRAN 202,which includes a 3G UE 202 a, nodeB 202 b, RNC 202 c, and femto gateway(FGW, which in 3GPP namespace is also known as a Home nodeB Gateway orHNBGW) 202 d. 4G is represented by EUTRAN 203, which includes an LTE UE203 a and LTE eNodeB 203 b. Wi-Fi is represented by Wi-Fi access network204, which includes a trusted Wi-Fi access point 204 c and an untrustedWi-Fi access point 204 d. The Wi-Fi devices 204 a and 204 b may accesseither AP 204 c or 204 d. In the current network architecture, each “G”has a core network. 2G circuit core network 211 includes a 2G MSC/VLR;2G/3G packet core network 212 includes an SGSN/GGSN (for EDGE or UMTSpacket traffic); 3G circuit core 213 includes a 3G MSC/VLR; 4G circuitcore 214 includes an evolved packet core (EPC); and in some embodimentsthe Wi-Fi access network may be connected via a 2G circuit core 215 witha 2G MSC/VLR. Each of these nodes are connected via a number ofdifferent protocols and interfaces, as shown, to other, non-“G”-specificnetwork nodes, such as the SCP 221, the SMSC 222, PCRF 223, HLR/HSS 224,Authentication, Authorization, and Accounting server (AAA) 225, and IPMultimedia Subsystem (IMS) 226. An HeMS/AAA 227 is present in some casesfor use by the 3G UTRAN. The diagram is used to indicate schematicallythe basic functions of each network as known to one of skill in the art,and is not intended to be exhaustive. Noteworthy is that the RANs 201,202, 203, 204 rely on specialized core networks 211, 212, 213, 214, 215,but share essential management databases 221, 222, 223, 224, 225, 226.More specifically, for the 2G GERAN, a BSC 201 c is required for Abiscompatibility with BTS 201 b, while for the 3G UTRAN, an RNC 202 c isrequired for Iub compatibility and an FGW 202 d is required for Iuhcompatibility.

FIG. 3 is a schematic network architecture in accordance with someembodiments. The architecture shown is an exemplary “brownfield”deployment architecture, i.e., an architecture being deployed usingexisting equipment and assets, and adds a virtual RNC gateway (VRNCGW)301, which can be a Parallel Wireless HetNet Gateway, or othervirtualizing, coordinating, and base station managing node. 2G RAN(GERAN) 302, with mobile station (MS) 302 a and BTS 302 b, isrepresented, but an Abis interface is made directly between GERAN 302and gateway 301. 3G RAN (UTRAN) 303, with UE 303 a and base station 303b, connects directly to gateway 301 via Iuh or Iub without an RNC, asthe gateway handles the RNC functions. If a nodeB is used, the Iubprotocol may be used; if a home NodeB or femto is used, the Iuh protocolmay be used. 4G RAN (EUTRAN) 304 is represented by UE 304 a and eNodeB304 b, which communicates via S1 to the gateway 301; S1 is theprotocol/interface used for eNodeBs in communicating with the LTE basestation managing node, the MME. A Wi-Fi RAN 305, including Wi-Fi device305 a and AP 305 b, using SWu, is also directly connected to VRNCGW 301,which permits it to be part of the mobile operator network. Instead ofSWu, S2a and S2b may also be used; S2a may be used by/for a trustedwireless access gateway (TWAG), and provides a single IPsec tunnel,while S2b is used for interacting as an evolved packet data gateway(ePDG), which is an untrusted gateway that permits multiple IPsecsessions to be opened.

Gateway 301 handles all protocol communications with the inner corenetwork. It may send 3G sessions to either the 3G packet core 311 or the3G circuit core 312, or 4G sessions to the 4G packet core 313, orcircuit-switched fallback (CSFB) sessions to 3G circuit core 312.Authentication, location registration, or packet-based VoIP etc. ishandled according to the prior art by PCRF 314, AAA 315, SCP 321, SMSC322, HLR/HSS 323, IMS 324 as usual. By the action of the gateway 301 asa virtualizing proxy, extraneous details of the RAN are hidden from thecore network and vice versa. The gateway is also enabled to performsteering or slicing as appropriate, so that certain UEs or base stationscan be directed to other “Gs” (RANs) or resources can be split amongnetworks. The 2G GERAN core network has been eliminated, as all 2Gsessions can be handled by the 3G core. Although the legacy GERANrequires that the gateway 301 use Abis, the core network may view thelegacy 2G MS's as 3G UEs. The VRNC may provide both a virtual RNC and aHNBGW, in some embodiments, thus enabling RAN virtualization andcoordination for both 3G and 4G nodes. The VRNC may also provide avirtual BSC in some embodiments for legacy GERAN base stations.

This architecture has the following advantages and characteristics, insome embodiments. By having the different RANs share a single gatewayand by having UEs/MS's share core networks, less complexity is requiredin the core and operators are not required to keep multiple corenetworks active. A heterogeneous network is enabled to be usedefficiently. As well, although implementation of the gateway 301requires increased complexity, this results in additional potential forfeatures to be added, such as coordination features across RANtechnologies. By terminating connections, lower-layer encryption istypically not in place, allowing for deep packet inspection and lawfulintercept (although application-layer encryption is still potentially inplace).

FIG. 4 is a schematic network architecture in accordance with somefurther embodiments. The architecture shown is an exemplary “greenfield”deployment architecture, i.e., an architecture being deployed with newpurchases of equipment to provide coverage in areas previously notserved by existing equipment. 2G GERAN 402, with MS 402 a, BTS 402 b; 3GUTRAN 403, with UE 403 a and nodeB 403 b; 4G EUTRAN 404, with UE 404 aand eNodeB 404 b; and Wi-Fi access network 405, with mobile device 405 aand AP 405 b, are still present and each continue to go through VRNCGW401. However, in this configuration it is not necessary to provide a 3Gpacket core or circuit core. Instead, a 4G packet core 410 is provided,as well as functions for enabling the 4G core: AAA 411, PCRF 412, HSS413, and IMS nodes P/I/S-CSCF 414, wireless TAS 415, IP-SM-GW 416, andIM-SSF 417. The IMS core provides voice calling functions and the 4Gpacket core provides data calling functions.

VRNCGW 401 enables this core network simplification in conjunction withenhanced base stations in the RAN. Instead of legacy 2G and 3G basestations, Parallel Wireless CWS/BTS 402 b and Parallel WirelessCWS/nodeB 403 b provide additional functionality. CWS/BTS 402 bcommunicates with 2G MS 402 a using an A interface, but instead ofrequiring Abis, CWS 402 b may interwork the A interface and providevoice calling using RTP and SIP via IMS, thus requiring only a standardpacket-switched session that 4G core network 410 can provide. ParallelWireless CWS/nodeB 403 b may interwork CS sessions similarly to IMS.CWS/BTS 402 b and CWS/nodeB 403 b both only require Iuh to be handled byVRNCGW 401, such that the VRNCGW is required only to use Iuh andS1/S2/SWu.

Although not shown, it is apparent that this network architecture isflexible and accommodates a variety of configurations. The generalapproach being used here is to provide a stateful proxy at the gatewaythat is capable of handling a particular protocol/interface. Since thegateway sits at the center of the network for both the RAN (andtherefore the UE or mobile device) and the core network, the statefulproxy can have appropriate knowledge about the messages that have beensent. The stateful proxy can also suppress messages, change headers,insert messages, or perform other proxy functions. A finite statemachine (FSM) may be used for handling state, which may be tracked formobile devices (MS, UE, etc.) or base stations (nodeB, ENB, HENB, Wi-FiAP, etc.) as well as the core network nodes themselves.

In some embodiments, methods for coordinating between base stations arealso available using X2, Iur, and Iurh protocols. The X2 interface isused between 4G eNodeBs. The Iur interface is used between RNCs. Usingthe VRNCGW as a proxy and gateway, the VRNCGW may be able to provideIur-based nodeB coordination with other RNCs, as well as interworkingbetween X2 and Iur for heterogeneous RAT coordination. The VRNCGW mayalso use Iurh interface to exchange coordination information with homenodeBs as a HNBGW. This type of signaling enables features such as softhandover, direct handover, COMP, ICIC, and others. Proxying andaggregation of these interfaces at the VRNCGW has also been considered.

FIG. 5 is a schematic network architecture showing security andsignaling characteristics in accordance with some embodiments. 3G nodeBs501 and 502 are connected via Iuh/Iurh to VRNCGW 503. An enhancedmessaging service (EMS) server 504 is also connected to VRNCGW 503 forproviding text messaging and other services. VRNCGW provides 3Gself-organizing network (SON) capability, HNBGW capability, and securitygateway capability to RANs 501 and 502. RAN 501 is connected over aWi-Fi backhaul link; RAN 502 is connected via a physical link or anotherlink. Both RAN 501 and 502 have opened IPsec tunnels to VRNCGW 503,which terminates the tunnels and decrypts the contents. VRNCGW 503, viaits security gateway (SeGW), then takes the output of the tunnels andsends them via additional IPsec tunnels that connect to, in thisparticular network configuration, an RNC 505 (via Iur for inter-RNCcoordination), an SGSN 507 (via IuPS for delivery of packet traffic),and an MSC 506 (via IuCS for delivery of circuit-switched calls). Thesenodes 505, 506, 507 are in the 3G core network, and no additionalsecurity is needed between these nodes and other nodes in the corenetwork. MSC 506 connects to the regular telephone network, e.g., thePSTN 508, to provide call connectivity. SGSN 507 connects to GGSN 509,which connects to the public Internet 510.

Components

The Parallel Wireless solution may include the following components:

Converged Wireless System (CWS)—the CWS component is a multi-technologybase station with an integrated backhaul (wired, microwave, mesh andLTE) that supports LTE, and LTE Advanced, 3G, and Wi-Fi access,simultaneously. The CWS series is available in different form factorssuch as outdoor, in-vehicle small cell, and indoor.

HetNet Gateway—the HetNet Gateway (Parallel Wireless HNG) is acarrier-grade server that is NFV/SDN-based, 3GPP-compliant RANorchestrator that enables RAN hyperconnectivity by unifying anytechnology (3G, 4G, Wi-Fi), any vendor RAN by presenting it as onecommon interface to the core. Parallel Wireless HNG logically sitsbetween the RAN and the core and abstracts the RAN on COTS hardwarewhile making the RAN self-configuring, self-optimizing, andself-healing. To provide hyperconnectivity and to manage the RAN inreal-time, the Parallel Wireless HNG combines these virtualized networkfunctions: virtual-eNB, HeNBGW, X2 gateway, HNBGW/vRNC, ePDG,TWAG/SaMOG, SON server, edge/cell site aggregation, and the securitygateway. It is also an Internet of Things (IoT) enabler, and eMBMSenabler by adding MCE and MBMS-GW functionality and analytics. Itoptimizes the signaling and data traffic going to core network to allowoperators to scale the network to meet growing capacity demands at lowcost. In an LTE network, the HetNet Gateway (Parallel Wireless HNG) nodelogically sits between the eNodeBs and the MNO Evolved Packet Cores(EPCs). It orchestrates thousands of base stations to look like a singleone to the MNO packet core. The Parallel Wireless HNG virtualizes theradio network resources such as eNodeBs and backhaul and makes themself-configurable and self-adjustable. It acts as HeNBGW andvRAN/virtualENB. It allows plug and play operation of CWS nodes and meshbackhaul, and allows them to form an ad hoc network as the nodes come into the network and leave. In a 3G network, the Parallel Wireless HNGprovides the Home Node B Gateway and virtual RNC functionality. ForWi-Fi, the Parallel Wireless HNG acts as a Wireless LAN Controller(WLC), Evolved Packet Data Gateway (ePDG) and Trusted Wireless AccessGateway (TWAG). These are all configurable options and one or the othercan be configured based on an operator's requirements. In someconfigurations Parallel Wireless HNG also acts as an EPC. The HetNetGateway sits between the RAN and the core network, and as a result is ina position to provide proxying and virtualization for any-G and for anycore or multiple cores, as well as being able to perform deep packetinspection and lawful intercept for data flowing through the networkthat would be encrypted if intercepted at a different point in thenetwork.

Uni-Manage—the Uni-Manage software is an Element Management System (EMS)for the CWS and HetNet Gateway (Parallel Wireless HNG) components, andprovides a web-based Graphical User Interface (GUI) for operators tomanage and monitor the network elements.

In some embodiments, a Parallel Wireless CWS may be used to provide 3GRadio Access, providing WCDMA air interface network interfaces for theCWS towards 3G core. When using the CWS, or another small cell or femtonode, it is possible in some embodiments to use the Iuh or Iur protocolto effectively provide 3G configuration and control for those nodes.When providing configuration and control for traditional 3G macro cells,the commonly-used Iub interface is supported by the Parallel WirelessHNG as well, and the Parallel Wireless HNG acts as the RNC for such abase station. In some embodiments, Iub and Iuh may be enabled at thesame gateway. In some embodiments, a lower-level radio L1/L2 layer maybe implemented in a hardware or software module on the Parallel WirelessCWS, or a software state machine for handling L1/L2 messages at theParallel Wireless HNG.

Features of IuGW

In some embodiments, Parallel Wireless HNG may act as or provide an IuGwfunctionality. It may also encompass 3G SON and security gateway. Insome embodiments, CWSes are virtualized by which HNB endpoint (towardsexternal HNBGW) would be configured. There could be multiple CWSesvirtualized per HNB endpoint or it could be a single CWS (macro handover). In some embodiments, Parallel Wireless HNG may register largenumber of UEs (could be in thousands) from one HNB endpoint. HNBGW willbe capable of supporting large number of UEs behind one HNB node. Insome embodiments, a SON module may provide the functionality toprovision CWS with information like Cell-ID, PSC and other OA&M details.SON may provide API to validate CWS attributes at the time of HNBregistration. SON features may be enabled in some embodiments, such as:MRO—Iurh based, Outage Detection & Compensation, Coverage and CapacityOptimization, Energy Savings, Modification of Antenna Tilts, ICIC. Insome embodiments, mobility optimization (a SON feature) may be enabled.In such an embodiment, Parallel Wireless HNG will be acting as Iur &Iurh proxy concentrating handovers. In such configuration handovers willbe performed directly from the MACRO RNC to Parallel Wireless HNGbypassing 3G core network. In some embodiments, IuGw may exposeindividual CWS to HNBGW. So in a deployment scenario, there will be aset of CWSes which are emulated one-to-one with external HNBGW and therewill a set of CWSes which as a group is emulated as one HNB withexternal HNBGW. The CWSes may be grouped in various ways. In someembodiments Parallel Wireless HNG based HNBGW uses CWS grouping tovirtualize resources and allow flexible and auto assignment of LAC/SACetc. In some embodiments Parallel Wireless HNG based HNBGW uses CWSgrouping for RTP localization for a set of CWSs.

In some embodiments, this IuGW provided by the HetNet Gateway may bemore than a simple router or proxy. Instead, the IuGW may handle Iub forcommunicating with 3G macro base stations, Iuh for communicating withHome NodeBs, or both in the same gateway, typically as separate softwaremodules or sharing a state machine for tracking the behavior of the UE.In some embodiments this is done by providing a virtual RNCfunctionality at the base station. The virtual RNC functionality may bea complete software-virtualized RNC, in some embodiments, but may be asoftware state machine-driven proxy, in other embodiments, tracking thestate of the remote nodeB as well as any attached UEs. The virtual RNCmay communicate with other RNCs, virtual or non-virtual, or HNBGWs viaIur, and may communicate to HNBs using Iurh as well. The virtual RNC mayterminate any tunnels needed to provide service to the UE. For example,the VRNC may act as a endpoint for a GTP-U tunnel carrying user data toa SGSN in the core network.

In some embodiments, the IuGw may run as part of Parallel Wireless HNG(LTE Access Controller, the Parallel Wireless controller node); may usethe Parallel Wireless HNG build environment and scripts; Binaries mayget packaged as part of unicloud rpm; may run as part of ‘pwbootd’service; may use UniTask framework for process management; may useParallel Wireless HNG confd CLI for configuration and statisticsmanagement; may use Parallel Wireless HNG alarm framework for alarmgeneration; and may use Parallel Wireless HNG logging framework forlogging and for managing logging level. In some embodiments, Loaddistribution for control plane traffic may be implemented. Control planetraffic concentration towards external 3G core may be implemented. IuGwmay forward user plane packets as UDP proxy using kernel module or dpdk.The IuGw proxy may be extended to full-fledged HNBGW running in ParallelWireless HNG. But it is not expected to run HNBGW and Iuhproxy on thesame Parallel Wireless HNG at the same time.

In some embodiments, deployment model here means that, criteria used forgrouping multiple CWS-HNB's as single HNB, how many such grouping wouldbe made and how are the cell-ids allocated to CWS and how they aremapped on the interface to HNBGW, etc. Group configuration may be usedto associate one or more CWS and one HNB in it. When a message entersthe Parallel Wireless HNG, group name for that message will beidentified and tagged with the message. This group name is used by allprocess to identify required configurations and ingress/egress SCTPconnections, etc. Parallel Wireless HNG need not interface with externalHNB Management System (HMS), in some embodiments.

In some embodiments, an OAM may be included that contains: EMScommunicating with Parallel Wireless HNG using NetConf Interface andpresenting CWS & Parallel Wireless HNG Data Models; HMS Server; aParallel Wireless HNG translation function providing interworkingbetween the ConfD and Iuh provisioning; and SON features.

In some embodiments 3G Radio Access CWS, providing WCDMA air interfaceand Iuh interface towards HNB GW; Parallel Wireless HNG functionality,first phase deployment Parallel Wireless HNG will be playing multiplefunctions: IuGw; 3G SoN; SeGW—Security requirements contain bothrequirements for the IPsec, securing communication between the CWS nodeand the Parallel Wireless HNG where Parallel Wireless HNG is acting asSeGW, CWS WCDMA over the air security; and L2 WiFi Mesh security; OAM,that contains: EMS communicating with Parallel Wireless HNG usingNetConf Interface and presenting CWS & Parallel Wireless HNG DataModels; HMS Server providing TR-069 support; Parallel Wireless HNGtranslation function providing interworking between the ConfD and Iuhprovisioning; SoN features (such as MRO (Inter WCDMA only and statisticsbased), ANR, and PCI Planning & Optimization).

Supported in some embodiments: circuit-switched fallback (CSFB) fromthird party 4G Macro; CSFB from 4G CWS; Intra Frequency Handovers CNanchored; Inter Frequency Handovers CN anchored; Inter RAT HandoversParallel Wireless HNG anchored; Intra Frequency Handovers ParallelWireless HNG anchored; Inter Frequency Handovers Parallel Wireless HNGanchored; Inter RAT Handovers Parallel Wireless HNG anchored. Alsosupported in some embodiments is maintaining the continuity of UEsupport during RNSAP Relocation by transferring the information from theSource HNB to the Target HNB according to the section 5.10 of 3GPP TS25.467 V11.1.0.

RANAP signaling is used to establish the Radio access bearers (RABs) insome embodiments. RAB-Assignment Request of RANAP carries all thedetails of the RABs. This message is usually carried inside the RUADirect-Transfer message (except in the case of relocation).

Additional features in some embodiments include: Aggregation of theIPsec connections from the CWSs towards 3G Core; Aggregation of SCTPConnections from the CWSs towards 3G Core; Virtualization of the 3GNetwork; Radio resource management as RNC; Paging and handoveroptimization for smallcells managed by IuGW; Enable localized services,differentiated QoE for a group of NodeBs such as RTP localization.

Registration

At service start up Parallel Wireless HNG registers all the configuredHNBs with external HNBGW. When CWS does a HNB registration it is locallyprocessed and accepted by Parallel Wireless HNG. When the UE registersfrom CWS, it forwards the UE registration towards HNBGW after replacingrequired IEs. When service starts up, HGWCon performs HNB registrationfor configured HNBs with external HNBGW. When CWS does a HNBregistration HNBCon processes and accepts the registration. When a UEregister message is received at HNBCon, it selects a UEMgr and forwardsit to that instance. HNBCon will tag this message with the group basedon configuration and forward to UEMgr. At UEMgr a new entry for this UEis created and forwards it to HGWCon. At HGWCon it identifies the HNBfor the group name and forwards the UE registration.

Mobility

Mobility between two different CWS Groups. When a UE moves between twodifferent CWS groups external HNBGW needs to be informed. When ParallelWireless HNG receives the ‘Relocation Request’ it maps the CWS ID andCell ID to the corresponding HNB-ID and Cell ID for external HNBGWinterface and forwards it to HNBGW. When it receives response it maps itback to the CWS interface IDs and forwards it to CWS. For all themobility control plane messages Parallel Wireless HNG does the similarmapping and forwards it accordingly.

Internally for the mobility scenario, UEMgr maintains the mobility FSMstates. When HGWCon forwards the message to external HNBGW it replacesthe cell-id with correct cell-id as required for HNBGW interface.Similar call flow will apply for mobility with macro zone. Mobilitybetween two CWS of same group—Node Level Call Flow. When a UE movesbetween CWS of same groups, no need to inform external HNBGW about themovement. Parallel Wireless HNG locally anchors the mobility.

Topology Hiding and Grouping

In some embodiments, the use of a virtualizing gateway may solve theproblem of an increased number of small cells, to provide more capacity,more users, more handovers, and more load on the core. The ParallelWireless HNG virtualizes small cells A, B, C, D to appear only as smallcell A. Suppose RF planning isolates cells B, C, D from macro. Macrohands over to and from cell A. Cells B, C, D hand over to A and to eachother. All handovers to and from B, C, D are advantageously hidden fromthe core. In such embodiments, the topology of the network may be hiddento improve handover performance. For example, a macro base station thatcan cover a large area may be preferable to a scattered set of smallcell base stations when traveling at high speed on a highway, but thesmall cell coverage area may be preferable when moving at walking speed.Hiding certain small cells can result in avoiding unneeded andundesirable handovers.

In some embodiments, grouping of a set of nodes is performed. A proxycan be used to enable small cells to connect to a core network. However,a problem with a simple proxy is that some mobility scenarios requireindividual CWSes (small cells) to be exposed to the core. The examplesof such scenarios are as shown herein. Specifically, when a two-stagehandover is made available as shown herein with some cells constitutinga “rural zone” and some cells constituting a “macro zone,” it isdifficult to proxy all individual cells as a single cell, because someof the “rural” cells are not adjacent to the macro and cannot be proxiedtoward the core as if they were a single cell adjacent to the macro.

The solution to this problem is to provide flexible grouping of cellstoward the core. Some CWSes are emulated 1:1 with the HNBGW. Others areemulated as a virtualized group. This mapping may be configuredstatically or dynamically, such as being allocated from a pool. Each CWShas a unique CGI. Each CWS can be assigned its own location area code(LAC), service area code (SAC), and routing area code (RAC), as definedin, e.g., 3GPP TS 23.003, V9.15.0 hereby incorporated by reference,which are identifying parameters for small cells; however, based on whatis needed, some of these parameters may be shared among CWSes, andmultiple CWS can share one or more of these identifiers via a commonprofile. In some embodiments, multiple vRNCs and RNC IDs may besupported. Allocation of groupings to cells may be performed at acontrol node, such as at the Parallel Wireless HNG or HetNet Gateway.The cells may receive their configuration using X2, NETCONF, or anyother control channel. The cells need only be made aware of their owngrouping. The advantages of this are that certain local actions arethereby enabled by the local nodes, such as base station/HNB and UERegistration and mobility between two different small cell groups, asdescribed herein. In some embodiments, the location of each small cellbase station (CWS) may be tracked. Each CWS's CGI may be mapped tolat/long. Location information can be provided for CWS as CWS has GPS.The Parallel Wireless HNG acts as downstream system using CGI tocross-refer to originating cell. 3GPP location based services (LBS)support for emergency calls may be provided. In some embodiments,geographic location may be used to create groups, which may then be usedto perform targeting of ads, disaster warnings, text messages to allsubscribers, etc. In some embodiments, MBMS functions may be performedon individual groups to provide, e.g., localized broadcast. In someembodiments, backhaul may be managed and optimized on a per-group level.Other optimizations may be performed within groups or subgroups.

To support topology hiding feature, Parallel Wireless HNG may hide theCWS IP addressing/ports towards the 3G core and vice versa. This meansthat the RAB Assignment Request coming in from 3G core will beterminated at Parallel Wireless HNG. Parallel Wireless HNG will storethe parameters of the RAB including the transport layer informationprovided by 3G core. Parallel Wireless HNG will then originate newrequest towards the CWS such that it contains transport layerinformation specific to Parallel Wireless HNG. When the CWS replies withRAB Assignment Response message, Parallel Wireless HNG will again storethe parameters provided by CWS and send a response to the HNBGW that mayinclude Parallel Wireless HNG assigned transport network layerparameters. When the data starts flowing through the Parallel WirelessHNG, it will appropriately proxy the data from one side to the otherside based on the control information of how transport networkparameters were assigned for a given bearer.

Each set of CWS that is represented as one virtualized HNB (akaoperator-network) will be configured with its own ingress user-plane IPaddress and egress user-plane IP address. User plane IP address can besame as control plane IP address because user plane is over UDP whilecontrol plane uses SCTP. However, typically it needs to be ensured thatthis same IP is not used elsewhere in the system (e.g. SON/Configmg linketc) where it can now or in future cause conflicts due to UDP port rangeclash. Note that ingress and egress user-plane IP addresses need to bedifferent. In Phase-1, Parallel Wireless HNG will allow configuration ofonly one user plane IP address at ingress and one at egress. In future,we may allow multiple user-plane IP addresses. For each bearer within anoperator-network, Parallel Wireless HNG will allocate one pair of UDPports. This will be communicated to both the CWS as well as to the 3Gcore in RAB Assignment Request/Response messages. When the peers senddata packets to Parallel Wireless HNG for the given bearer, they will bedestined to this UDP port and the IP address of user-plane ingress oregress. Based on the IP address, Parallel Wireless HNG will be able tofind out the direction and based on the UDP port number, it will be ableto find out the bearer. Mapping information will be available which itwill then use to proxy the packet out with appropriate parameters. Whileallocating UDP port number blocks, Parallel Wireless HNG would leave outthe initial system port range. E.g. The port allocation will start after1024. The first bearer to get created can get the port number 1026(first even port after 1024). If PS user-plane is also running on thesame IP address then GTP is going to use UDP port 2152. So that port maybe left out.

Control Plane and User Plane

Parallel Wireless HNG acts as vRNC/HNBGW. While acting as vRNC itinterfaces with outdoor NodeBs (pico, micro, metro) over Iuh interface.It does radio resource management as a typical RNC because it hasvisibility of all the radio nodes and their resources. It presentsstandard based interfaces towards MSC and packet core such as Iu-CS andIu-PS. The HNBGW serves the purpose of a RNC presenting itself to the CNas a concentrator of HNB connections. The interface between CN and theHNBGW serves the same purpose as the interface between the CN (CoreNetwork) and a RNC. Parallel Wireless HNG also performs 3G SON functionsfor PSC allocation and ANR table management. It also provides plug andplay function for 3G node as well as dynamic RF power adjustment.

HNBGW segregates Control Plane & User Plane traffic for performanceenhancement. User plane is further divided into CS and PS user planetraffic.

User plane. In some embodiments, regarding circuit switched (CS) callsetup and data transfer, HNBGW CS user plane is responsible for relayingRTP packets in uplink and downlink directions. In some embodiments,vRNC/HNBGW supports the transport of signaling and data messages over IUand Iuh interfaces for successful CS call establishment and datatransfer. Mentioned below are the messages supported: Iuh signalingmessages using HNBAP over SCTP: HNB REGISTER REQUEST/ACCEPT/REJECT; HNBDEREGISTRATION; UE REGISTRATION/ACCEPT/REJECT; UE DEREGISTRATION; ERRORINDICATION. Iuh signaling messages using RUA over SCTP CONNECT; DIRECTTRANSFER; CONNECTIONLESS TRANSFER; DISCONNECT; ERROR INDICATION. NASsignaling transfer via RANAP message: INITIAL UE MESSAGE; DIRECTTRANSFER; IU RELEASE REQUEST/COMMAND/COMPLETE; RAB ASSIGNMENTREQUEST/RESPONSE; RAB RELEASE REQUEST; RAB MODIFICATION REQUEST;RELOCATION REQUIRED/COMMAND/FAILURE; RELOCATION REQUEST/REQUESTACK/FAILURE; RELOCATION COMPLETE; RELOCATION DETECT; RELOCATIONCANCEL/ACK; PAGING; COMMON ID; RESET/RESET ACK; RESET RESOURCE/RESOURCEACK; ERROR INDICATION; SECURITY MODE CONTROL. In some embodiments,regarding packet switched (PS) call setup and data transfer, Thesignaling messages mentioned with respect to CS would also be supportedfor PS domain. For data transfer during PS call, HNBGW user plane for PSdomain is responsible for relaying GTP packets in uplink and downlinkdirections.

For the user plane, in some embodiments, Parallel Wireless HNG as IuGWwill support both circuit-switched (CS) data proxy and packet-switched(CS) data proxy modes.

For the CS User Plane, in some embodiments, voice or video stream datawill be encoded inside RTP protocol. RTP will be carried over UDP overIP transport. RTCP may be used but is optional. The receiving entity mayignore incoming RTCP PDUs. RTCP is again carried over UDP over IPtransport. Each transport bearer is identified by the UDP port numberand the IP address (source UDP port, destination UDP port, source IPaddress and destination IP address). Parallel Wireless HNG will need toreserve two consecutive ports per transport bearer (one for RTP andanother for RTCP). Pair of two ports is referred as port number block.For RTP protocol, an even numbered UDP port is used. RTCP uses theconsecutive odd numbered port.

Transport layer information for CS plane in RANAP protocol includes‘transport layer address’ and ‘Iu Transport association’. Transportlayer address contains IP address encoded in NSAP(Network-service-access-point) structure as per RFC 4548.Iu-Transport-Association will contain the UDP port inside the Binding-IDfield. This UDP port will be an even numbered port to be used by RTPprotocol.

Voice/video packets are usually very short (approximately less than 100bytes). For every bearer of every user, sending the small packetsincreases the overall link bandwidth requirement because of overhead(UDP/IP) of transferring each packet. Also for the receiving end, packetrate will become a parameter for its overall capacity. To solve this,3GPP has proposed multiplexing scheme where the 3G core advertises onlyone UDP port (called RTP mux port) to the HNB. HNB then collatesmultiple RTP packets (could be of different users) and forms a biggerpacket (which contain smaller RTP chunks and additional multiplexingheaders). HNBGW receives this bigger packet and it then de-multiplexesthe RTP chunks for processing. Multiplexing is defined only in uplinkdirection. Secondly, it is optional. If the HNB does not supportmultiplexing, it can still keep sending the uplink RTP streams as perthe RAB assignment ports and ignore the RTP mux port. In the firstphase, Parallel Wireless HNG behaving as virtual HNB will ignore the RTPmultiplexing if any offered by the 3G core.

HNBGW may support the transfer of short message services (SMS) betweenUEs, in some embodiments, including: SMS-MT: message sent by the UE;SMS-MO:message sent to the UE.

Control Plane. In some embodiments, the control plan acts as follows.The control plane handles signaling messages and manages the TNL addresstranslation, RTP Port/GTP-U TEID management (Tunnel Endpoint Identifier)and sends the TNL address translation updates to user plane applicationover the propriety interface. The circuit-switched user plane handlesthe TNL address translation updates, create/delete/modify RTP session inboth HNB and CN direction, processes and forwards RTP data packetstowards HNB/CN. The packet-switched user plane handles the TNL addresstranslation updates, create/delete/modify GTP-U tunnel in both HNB/NBand CN direction, processes and forwards GTP-U data packets.

HNBGW supports hand-out and hand-in of on-going calls to/fromneighboring cells, in some embodiments, including CS Handover(relocation of context to/from neighboring cells for on-going voiceconversations) and PS Handover (relocation of context to/fromneighboring cells to on-going data sessions). When UE moves betweenCWSes of same group, location reporting and path switching may beimplemented.

HNBGW provides access control for HNBs/UEs based on white listconfiguration, in some embodiments. White list shall contain IMSI andHNB ID information. When the white list configuration is enabled, onlythose HNBs/UEs included in the list are allowed to access HNBGWresources. On the other hand, when disabled, any HNB/UE is allowed toaccess the HNBGW.

FIG. 5 is a schematic network architecture showing security andsignaling characteristics in accordance with some embodiments.

FIG. 6 is a schematic network architecture showing base station groupingin accordance with some embodiments. VRNCGW 611 sits in the networkbetween the RAN and the core network, which here is a 3G core 612.Several base stations, 601, 602, 603, 604, 605, 606, 607, 608, 609, 610are shown. Base stations 601, 602, 603 are handled separately from basestations 604, 605, 606, 607, 608, 609, 610. This is because basestations 604, 605, 606, 607, 608, 609, 610 are in a “virtual zone” 613,which has been designated as not permitted to perform handins from amacro cell. In a rural small cell deployment, this is to ensure thatmobile devices are not handed in when the result of a handin will be animmediate handout, or worse, a call drop due either to a small coveragearea or a coverage area that is not conducive to handing over to anothercell. The grouping method described with respect to this embodiment isapplicable to both 3G and 4G (LTE), although the base stations shown inFIG. 6 are 3G nodeBs. As shown in the interfaces between VRNCGW 611 and3G core 612, the VRNCGW communicates individually to each base station(here, using Iuh), but does not permit the core to address each of thevirtual zone base stations independently. Rather, all of the virtualzone base stations are treated as a single virtual cell with a specialID. As well, the virtual zone base stations are given a separate RNC IDas well, in some embodiments. In order for a handset or mobile device tobe handed over from a macro to one of the base stations managed by theVRNC, the handset must be handed over first to one of the regular basestations 601, 602, 603, and from there it can be handed over to any cellin the virtual zone. This is shown visually in the next figure and isreferred to as two-stage mobility.

FIG. 7 is a schematic base station deployment topology diagram, inaccordance with some embodiments. Shown is a typical “Rural Deployment”.In this type of deployment CWSs are used mainly for coverageaugmentation (not for the data offload under the overlaying macrocoverage). Current WCDMA release concentrates on “Rural” type ofsolution only. The cell IDs are different than shown in FIG. 6, but thefigure reflects a similar type of deployment. The grouping methoddescribed with respect to this embodiment is applicable to both 3G and4G (LTE), and either a 3G NodeB or a 4G eNodeB may be consideredwherever a base station is shown in this figure. The method described isuseful for deployment of small cells or for underlay of small cellsunder a macro coverage area.

As shown in FIG. 7, not all Rural zone CWSs will have overlappingcoverage with the Macro Zone, hence in order to support sessioncontinuity, two-phase mobility may be required as shown in this figureand also in FIG. 10. Hand-in from Macro to neighboring CWSes (forexample hand-in between RAN A and CWS Cell_Id A. entering Rural zone) isa two-phase handover. HNG may be a VRNCGW or management gateway, and CWSmay be a multi-RAT node, in some embodiments.

Macro zone 701 includes macro 801 a, macro 80 ab, and macro 801 c, eachproviding coverage over a large area of a highway. The macro zone iscreated as a group in the VRNCGW or management gateway.

Rural zone 702 includes base stations 702 a, 702 b, 702 c, 702 d, 702 e,702 f, 702 g in HNG management area 702 x, and base stations 702 h, 702i, 702 j in HNG management area 702 y.

Handovers among the base stations shown in FIG. 7 fall into thefollowing categories: small cell to macro handovers, to or from RuralZone to Macro Zone; inter-small cell handovers within an HNG managementarea; and intra-HNG management area handovers. Each HNG management area702 x, 702 y may appear as a single macro base station to the corenetwork, in some embodiments, such that handovers between 702 x and 702y are handled like regular handovers, with the two HNGs transparentlyidentifying which cell the UE is in using the cell ID. For intra-HNGarea handovers, any notification of the handover may be suppressedtoward the core network, as from the perspective of the core network ahandover between two intra-HNG cells does not result in the UE movingfrom one eNB (or NB) to another eNB (or NB).

For handovers to and from the macro network, the handover zone for,e.g., macro 701 a only impinges on cell 702 a. So the HNG will notpermit a handover from the macro A to cells B, C, D, E, F, or G. This isa function of the coverage area of the cells. Otherwise handovers arehandled normally. Various other rules can be set up so that handoversare permitted under only desirable conditions.

Groupings may be performed in the VRNCGW across G's, in someembodiments. For example, the rural zone may include both 3G and 4Gcells, and handovers between them and a set of 3G macros in a macro zonemay be handled according to the described method. Multiple groups perHNG management area may be used in some embodiments. Groupings may bemade based on RF conditions, topological or geographical conditions,trains or highways or other features of the landscape leading toassumptions about user speed, or neighbor relation tables that relate tothe topology of the graph of the cells' coverage areas, or otherfactors.

Operation and Call Flows

FIG. 8 is a signaling call flow showing a handover of a circuit-switchedsession at a gateway, in accordance with some embodiments. UE 801 hasmoved from a first coverage area to a second coverage area, and attachesto a nodeB (not shown), which is controlled by source VRNC 802. SourceVRNC 802 is a VRNCGW, as described herein, proxying and serving as agateway for the nodeB to the 3G core network. The UE 801 requests to behanded over from its prior cell to this cell, and since this is acircuit-switched session, the relocation request is sent from the nodeBto the source VRNC 802 to the MSC 804 in the core network. The MSC 804then sends a message to target VRNC 803, which is the VRNCGW handlingthe UE's prior cell. Handover proceeds in the same manner as describedby the 3G standard; however, in some embodiments source VRNC 802 andtarget VRNC 803 are both VRNCGWs. In some embodiments source VRNC 802may be handling a nodeB using the Iub interface, and target VRNC 803 maybe handling a Home nodeB or a Parallel Wireless multi-RAT node using theIuh interface, or vice versa. In some embodiments both base stations maybe Iub or Iuh. In some embodiments, Iub and Iuh may be enabled bysoftware or hardware modules at the same VRNCGW. In some embodiments,inter-RAT handovers or steering between 3G and 4G may be enabled byhaving 3G and 4G modules on the same VRNCGW.

FIG. 9 is a signaling call flow showing a handover of a packet-switchedsession at a gateway, in accordance with some embodiments. UE 901 hasmoved from a first coverage area to a second coverage area, and attachesto a nodeB (not shown), which is controlled by source VRNC 902. SourceVRNC 902 is a VRNCGW, as described herein, proxying and serving as agateway for the nodeB to the 3G core network. The UE 901 requests to behanded over from its prior cell to this cell, and since this is apacket-switched session, the relocation request is sent from the nodeBto the source VRNC 902 to the SGSN 904 in the core network. The SGSN 904then sends a message to target VRNC 903, which is the VRNCGW handlingthe UE's prior cell. Handover proceeds in the same manner as describedby the 3G standard; however, in some embodiments source VRNC 902 andtarget VRNC 903 are both VRNCGWs. In some embodiments source VRNC 902may be handling a nodeB using the Iub interface, and target VRNC 903 maybe handling a Home nodeB or a Parallel Wireless multi-RAT node using theIuh interface, or vice versa. In some embodiments both base stations maybe Iub or Iuh. In some embodiments, Iub and Iuh may be enabled bysoftware or hardware modules at the same VRNCGW. In some embodiments,inter-RAT handovers or steering between 3G and 4G may be enabled byhaving 3G and 4G modules on the same VRNCGW.

In some embodiments, the solution may support handins from Macro Zoneaccording to section 5.9.4a of [1] (open access HNBs). For ConnectedMode Inbound Mobility for CSG UEs to CSG HNBs or to Hybrid Cells: seesection 5.9.2a of [1]; for Connected Mode Inbound Mobility for non-CSGUEs to CSG HNBs or to Hybrid Cells, see section 5.9.3a of [1] The handinsolution implementation may be based on Parallel Wireless HNG supportingMacro-to-Femto (M2F) handin using the Fan-out approach for RelocationRequest for pre-Rel-9 UEs (Macro-RNC can't identify target-Cell-id). ForEnhanced Relocation from Open Access and Hybrid CWS (HNBs) to RNC—seesection 5.11.2 of [1]; Enhanced Relocation from RNC to Open Access CWS(HNBs) see section 5.11.2.2 of [1]; Enhanced Relocation from RNC toHybrid CWS (HNBs) see section 5.11.2.3 of [1].

FIG. 10 is a signaling call flow showing a two-phase macro to rural zonemobility scenario, in accordance with some embodiments. In this example,a handover is shown between the Macro Zone (RAN A) and the Rural Zone(CWS Cell_id A). The method described and shown in this figure relatesto eNodeBs and LTE as well as to nodeBs and UMTS/3G, and also to anyother “G” radio access technology.

UE 1001 is initially attached to macro nodeB A 1002, which is handled byan RNC in the core network (not shown). Also available are IuGW 1003 (aVRNCGW) and CWS base stations 1004 and 1005. CWS 1004 has cell ID A. CWS1005 has cell ID B. Initially, UE 1001 is attached to macro 1002.However, upon performing measurement reports it becomes apparent thatthe signal of the macro is decreasing, and based on measurement reports,at step 1006 the source RNC (not shown) decides to initiate relocationto target CWS A 1004. Target CWS A 1004 is managed by IuGW 1003, thatis, IuGW 1003 is acting as the RNC for this CWS. The source RNC (notshown) sends a RANP Relocation Request with the identified target cell'scell_id=A. As shown in step 1007, the CWS A allocates resources for theUE, and at step 1008, detects the presence of the UE in its coveragearea. The rest of the handover proceeds normally per the 3G standard.The IuGW/VRNC acts as an RNC toward the source RNC, and also acts as anRNC toward CWS A 1004, to facilitate the handover.

FIG. 11 is a signaling call flow showing an Iuh anchored rural to ruralzone mobility scenario, in accordance with some embodiments. FIG. 11illustrates typical high level handover between the CWSs in the RuralZone (for example from CWS Cell_id A to CWS Cell_id B). The methoddescribed and shown in this figure relates to eNodeBs and LTE as well asto nodeBs and UMTS/3G, and also to any other “G” radio accesstechnology.

UE 1101 is initially attached to CWS A 1102, which is managed by IuGW1103, which is a VRNCGW as described herein. Also available is CWS basestation 1104, which is also managed by IuGW 1103. CWS 1102 has cell IDA. CWS 1104 has cell ID B. Initially, UE 1101 is attached to CWS 1102.However, upon performing measurement reports it becomes apparent thatthe signal of the macro is decreasing, and based on measurement reports,CWS 1102 decides to initiate relocation to target CWS B 1104. Asaccording to the standard, the source CWS 1102 sends a RUA DirectTransfer Connect request to the IuGW 1103. The IuGW/VRNC does not needto contact the core network to facilitate the handover, but responds bysimply replying with a RUA Direct Transfer relocation command to CWS1102. Once the handover is completed, with a RANAP Relocation Completemessage, the IuGW 1103 intercepts it and no message is sent to the corenetwork. Further messages to the UE from the core network will bedisambiguated and sent to CWS B. The HNBAP UE Deregister message fromCWS 1102 is also intercepted and silenced, e.g., not sent to the corenetwork.

FIG. 12 is a signaling call flow showing additional aspects of a ruralto rural zone mobility scenario, in accordance with some embodiments.Mobility between two CWS of same group—Internal Message Flow. Since theUE moves between CWS of same group, UEMgr doesn't map the CWS and CellIDs. It maintains the mobility FSM states, but instead of involvingexternal HNBGW it locally anchors the mobility. The FSM states for UEmobility between CWS of same group and different group will be differentand it would need two set of FSM transitions.

CWS-Src 1201, which is a base station, is controlled by an HNG,represented by internal modules HNBCon 1202 and UEMgr 1203. At step1205, a handover is requested to CWS-Dst 1204. At step 1206, the UEmgris aware of the state and determines that no mapping is needed with theHNBGW because the two CWSes are in the same group. At step 1207, UEmgr1203 replies with the relevant information for a RANAP relocationrequest, which is passed along by HnbCon 1208, and an additional RANAPrelocation command is sent at step 1209. Relocation is completed withoutsignaling to the core network.

FIG. 13 is a signaling call flow showing base station registration, inaccordance with some embodiments. CWS-2 1301 and CWS-1 1302 areconnected to HNG 1303, which is a VRNCGW as described herein. CWS-1 isstarted first, step 1304, and as part of initialization requestsidentifiers, e.g., LAC, RAC, SAC, and cell ID from the HNG, step 1305.It receives CellId 0x1234501. Next, CWS-2 is started, at step 1306. Whenit initializes and requests identifiers, at step 1307, it receives adifferent cell ID, CellId 0x1234502, which is used thereafter todistinguish the cell at the HNG.

FIG. 14 is a schematic architecture diagram of an exemplary base stationtogether with an exemplary gateway, in accordance with some embodiments.Exemplary CWS base station 1401 includes LTE protocol modules 1401 b, RFmanager 1401 c, OAM manager 1401 d, and platform manager 1401 e, each ofwhich is managed as part of a baseband processing (BBP) module 1401 a.Additionally, address manager 1401 g, Wi-Fi access and mesh manager 1401h, and Config/SON module 1401 i are part of a general purpose processing(GPP) module 1401 f. A single IPsec secure tunnel 1403, in someembodiments, connects the CWS to the HNG 1402. HNG 1402 includes a HomeNodeB manager 1402 a, core network module/HGWcon 1402 b, UE managers1402 c, SON coordinators 1402 d, config manager 1402 e, Wi-Fi manager1402 f, and IPsec managers 1402 g. The modules are all stateful andshare data with each other. Multiple instances of each module arepresent, each with a connection to a distributed control path 1402 h.

The gateway has the following characteristics: distributed control planeacross multiple cores; distributed data path across multiple cores; nosingle point of failure for control and data processing; throttling tolimit traffic on a core; IP access control lists (ACLs) (static ordynamic or both); dynamic ACLs using an algorithm to detect a source IPsending invalid ISAKMP_INIT.

HNBCon and HGWCon interacts directly without UEMgr for non UE relatedmessages like Reset, Paging, etc. When UE is handed off, mobility FSMstates are maintained by UEMgr. HGWCon would have less intelligenceabout the CWS locations and mapping. It maintains the states of HNBconnection towards HNBGW and in a crude sense acts as a pipe towardsexternal HNBGW. This process may be replaced with a full-fledged HGWprocess in some embodiments. HNBCon will maintain HNB FSM states, UEMgrwill maintain HNB-UE FSM, IU FSM, RAB FSM states and HGWCon willmaintain HNB FSM for HNBGW interface. Neighbor table will be maintainedby SON and it will be used for allocating cell id related information.

RUA Connect Forking

In some embodiments, a PCI conflict may occur when two CWSes have thesame cell ID, in this case shown as Cell id A. The IuGw may gracefullyhandle the conflict by forking the RUA connect request. This results inboth CWS A's being requested to hand in the UE. However, only the CWSwith coverage in the physical region of the UE will be able tosuccessfully respond to the request, and the other forked RUA connectwill fail without negatively impacting hand-in.

In some embodiments, when a PCI conflict is detected, a handover requestmay be forked. Specifically, the handover request may be sent from thesource cell to all cells known to the source cell that have that PCI.Two or more handover requests, then, may be created. However, only onehandover request will ultimately be met/satisfied, because the receivingcell will determine either that the cell does contain the UE identifiedin the request and return a handover acknowledgement message, or thatthe cell does not contain the UE identified in the request and will failand/or not return a handover acknowledgement message. The handoverrequest may be sent either via X2 or 51, in some embodiments.

In small cell deployments there is a high probability of the PCIreuse—similar to PCI conflict—although PCI conflict normally means smallcells are close and there is a problem with UE sync up. So in case ofthe PCI reuse core network becomes confused on the reported targethandover cell site, as it doesn't know any better than PCI (physicalcell id) reported by UE. One commonly deployed method—network getsGlobal Cell Id (CGI) report from UE and uses global cell id instead ofPCI to resolve ambiguity—CGI is unique. Here a different and alternativemethod is proposed—we fork the handover message to all PCI (in case ofambiguity) and wait for one the CWS (can be third party as well we don'tcare) returning acknowledge. As soon as we get it, we continue with thehandover towards this specific small cell and drop other initiatedhandover sessions.

Further embodiments are contemplated. For example, algorithms fordetermining the intent of a user are contemplated, thereby enabling thenetwork to determine whether hand-in is desired. As another example, analgorithm based on the path vector, OSPF path vector, or determined UEspeed may be used for determining UE motion. As another example,admission priority may be influenced by one or more parameters. Asanother example, hand-in to a small cell may be rejected by immediatelyhanding back to a macro, based on hand-in parameters. As anotherexample, thresholds, such as reporting thresholds, cell selectionthresholds, and handover thresholds, may be monitored and set to reduceundesirable hand-ins. As another example, the control plane for the UEmay be anchored at the macro, while some hand-overs are handledtransparently via the IuGw. As another example, a macro overlay network,wherein a macro cell has coverage co-extensive with the coverage area ofthe small cells, may be configured with different hand-in parameters,such as minimal small cell hand-in. As another example, topology gapsmay be pre-configured to disallow handovers, such that if a networkidentifies the direction of travel of a UE as entering a small cell gapin coverage, handover from the macro is disallowed from certain sourcesmall cells or from the macro. Forking may involve creating more thanone copy, in some embodiments.

FIG. 15 is a signaling call flow showing handin with call connectmessage forking, in accordance with some embodiments. UE 1501 isconnected to macro RAN 1502, which is connected to a core network (notshown), and through IuGW 1503 to CWS Cell A 1504 and CWS Cell A 1505,both of which have the same Cell ID. At step 1506, the source cellinitiates relocation. This results in a RANP Relocation Request beingsent to the IuGW. The IuGW does not know which CWS is being requested,and as a result forks the request by sending a copy of the RUA connectrequest to each of cells 1504 and 1505. At step 1507, the IuGW starts atransfer timer. At step 1508, cell A allocates resources for the UE andat steps 1509 and 1510, the handover proceeds normally. By the operationof the handover and by cell 1504 returning messages, IuGW 1503 becomesaware that the UE is in cell 1504.

RTP Localization

The Real-time Transport Protocol (RTP) is a network protocol fordelivering audio and video over IP networks. RTP is used extensively incommunication and entertainment systems that involve streaming media,such as telephony, video teleconference applications, televisionservices and web-based push-to-talk features. RTP is one of thetechnical foundations of Voice over IP (VoIP), and in this context isoften used in conjunction with a signaling protocol such as the SessionInitiation Protocol (SIP) which establishes connections across thenetwork.

In some embodiments, RTP flows may be directed from one endpoint toanother endpoint within the control of the Parallel Wireless HNG,without requiring a session border controller to identify the need for,and provide, hairpin routing. The problem that exists in some situationsis that 3G calls require a session border controller even when the callis locally terminated. However, by providing this functionality at theedge of the network, the network may achieve better latency and otheradvantages.

The edge of network node may be the CWS or the Parallel WirelessHNG/Parallel Wireless HNG. The Parallel Wireless HNG/Parallel WirelessHNG may perform functions including endpoint lookup of call recipientwithin local area based on phone number; redirection of 3G call audio tocall recipient over RTP within a zone; and call termination. No MSC needbe involved. The call may be packet-switched or circuit-switched. Thecall can be a CSFB call; it may be terminated as CS by the CWS at eitherend of the call. Depending on the location of the edge of network node,this function may be performed within a group, across groups, or withina single CWS. Lawful intercept, 3-way calling, hold, conferencing, etc.may be managed by the Parallel Wireless HNG. The advantages may includelower call establishment latency, (lower call latency?), less load atupstream nodes, higher throughput, reduced backhaul requirements, andimproved voice quality as a result of the above.

FIG. 16 is a schematic network architecture diagram showing RTPlocalization, in accordance with some embodiments. CWS group 1/Virtualaccess network A 1601 is a group of CWSes managed by HNG 1604. CWS Group2/Virtual access network B 1602 is another such group, as is CWS Group3/Virtual access network C 1603. Also provided is 3G core 1605, which isin communication with HNG 1604. The HNG 1604 is an RNCGW and providesIuGW services. The HNG has an RTP localization policy, which is enforcedat the HNG. During CS call setup, the HNG determines the need for RTPlocalization and instructs the CWS by changing IP and port. Complete RTPlocalization 1606 (the CWSes are directed to communicate directlywithout going through the HNG), partial RTP localization 1607 (throughthe HNG), or no RTP localization 1608 (through the core) is detected asa possible condition and enforced at the HNG. Detection may be based onCWS groups, whether the cell ID is the same, whether the target ismanaged by the same HNG, or other factors.

FIG. 17 is a schematic diagram of a base station management gateway in aLong Term Evolution (LTE) architecture, in accordance with someembodiments. Base station management server 1701 provides services to,and is coupled to, eNodeB 1 1702 and eNodeB 17 1703, on a RAN side of anetwork (i.e., inside of the gateway). Base station management server1701 provides services to, and is coupled to, MME 1704, macro eNodeB1705, and macro eNodeB 1706, on a core network side of the network(outside of the gateway). Base station management server 1701corresponds to LAC 110, in some embodiments.

Within base station management gateway 1701 are self-organizing network(SON) module 1711, containing neighbor relation table (NRT) 1712 and UEmeasurement report processing module 1713; evolved packet core (EPC)module 1721, containing EPC finite state machine module 1722 and macroeNodeB table 1723; radio access network (RAN) module 1731, containingeNodeB finite state machine module 1732 and eNodeB table 1734; and userequipment (UE) module 1741, containing UE finite state machine module1742 and S1/X2 handover mapping table 1743. Each of modules 1711, 1721,1731, and 1741 are coupled to each other within base station managementgateway 1701, and may execute on one or more shared processors (notshown) coupled with memory (not shown).

In some embodiments, SON module 1711 may perform NRT maintenance, loadinformation processing and fractional frequency reuse (FFR) processing;RAN module 1731 may perform X2 association management with eNodeBs 1702,1703; EPC module 1721 may perform X2 association management with macroeNodeBs 1705, 1706; and UE module may perform X2 handover and S1/X2translation between eNodeBs 1702, 1703 and macro eNodeBs 1705, 1706. Allthe above managers/modules interact with each other to accomplish theassigned functionality.

FIG. 18 is a schematic diagram of a mesh network base station, inaccordance with some embodiments. Mesh network base station 1800 mayinclude processor 1802, processor memory 1804 in communication with theprocessor, baseband processor 1806, and baseband processor memory 1808in communication with the baseband processor. Base station 1800 may alsoinclude first radio transceiver 1810 and second radio transceiver 1812,internal universal serial bus (USB) port 1816, and subscriberinformation module card (SIM card) 1818 coupled to USB port 1814. Insome embodiments, the second radio transceiver 1812 itself may becoupled to USB port 1816, and communications from the baseband processormay be passed through USB port 1816.

A virtualization layer 1830 may also be included for mediatingcommunications with an evolved packet core EPC, specifically includingthe core network EPC (not shown) and local evolved packet core (EPC)module 1820. Local EPC 1820 may be used for authenticating users andperforming other EPC-dependent functions when no backhaul link isavailable. Local EPC 1820 may include local HSS 1822, local MME 1824,local SGW 1826, and local PGW 1828, as well as other modules. Local EPC1820 may incorporate these modules as software modules, processes, orcontainers. Local EPC 1820 may alternatively incorporate these modulesas a small number of monolithic software processes. Virtualization layer1830 and local EPC 1820 may each run on processor 1802 or on anotherprocessor, or may be located within another device.

Processor 1802 and baseband processor 1806 are in communication with oneanother. Processor 1802 may perform routing functions, and may determineif/when a switch in network configuration is needed. Baseband processor1806 may generate and receive radio signals for both radio transceivers1810 and 1812, based on instructions from processor 1802. In someembodiments, processors 1802 and 1806 may be on the same physical logicboard. In other embodiments, they may be on separate logic boards.

The first radio transceiver 1810 may be a radio transceiver capable ofproviding LTE eNodeB functionality, and may be capable of higher powerand multi-channel OFDMA. The second radio transceiver 1812 may be aradio transceiver capable of providing 3GPP WCDMA functionality. Bothtransceivers 1810 and 1812 are capable of receiving and transmitting onone or more bands. In some embodiments, transceiver 1810 may be capableof providing both LTE eNodeB and LTE UE functionality, and transceiver1812 may be capable of UMTS BTS functionality, UMTS UE functionality, orboth. The transceivers may be switched. Transceiver 1810 may be coupledto processor 1802 via a Peripheral Component Interconnect-Express(PCI-E) bus, and/or via a daughtercard. As transceiver 1812 is forproviding LTE UE functionality, in effect emulating a user equipment, itmay be connected via the same or different PCI-E bus, or by a USB bus,and may also be coupled to SIM card 1818.

SIM card 1818 may provide information required for authenticating thesimulated UE to the evolved packet core (EPC). When no access to anoperator EPC is available, local EPC 1820 may be used, or another localEPC on the network may be used. This information may be stored withinthe SIM card, and may include one or more of an international mobileequipment identity (IMEI), international mobile subscriber identity(IMSI), or other parameter needed to identify a UE. Special parametersmay also be stored in the SIM card or provided by the processor duringprocessing to identify to a target eNodeB that device 1800 is not anordinary UE but instead is a special UE for providing backhaul to device1800.

Wired backhaul or wireless backhaul may be used. Wired backhaul may bean Ethernet-based backhaul (including Gigabit Ethernet), or afiber-optic backhaul connection, or a cable-based backhaul connection,in some embodiments. Additionally, wireless backhaul may be provided inaddition to wireless transceivers 1810 and 1812, which may be Wi-Fi802.11a/b/g/n/ac/ad/ah, Bluetooth, ZigBee, microwave (includingline-of-sight microwave), or another wireless backhaul connection. Anyof the wired and wireless connections may be used for either access orbackhaul, according to identified network conditions and needs, and maybe under the control of processor 1802 for reconfiguration.

Other elements and/or modules may also be included, such as a homeeNodeB, a local gateway (LGW), a self-organizing network (SON) module,or another module. Additional radio amplifiers, radio transceiversand/or wired network connections may also be included.

Processor 1802 may identify the appropriate network configuration, andmay perform routing of packets from one network interface to anotheraccordingly. Processor 1802 may use memory 1804, in particular to storea routing table to be used for routing packets. Baseband processor 1806may perform operations to generate the radio frequency signals fortransmission or retransmission by both transceivers 1810 and 1812.Baseband processor 1806 may also perform operations to decode signalsreceived by transceivers 1810 and 1812. Baseband processor 1806 may usememory 1808 to perform these tasks.

Alternatives

In the present disclosure, the words “NodeB” or “eNodeB” are used torefer to a cellular base station. However, one of skill in the art wouldappreciate that it would be possible to provide the same functionalityand services to other types of base stations, specifically to BTSes,non-3GPP base stations, CDMA base stations, CDMA2000 base stations,Wi-Fi access points, and home eNodeBs (HeNodeBs), as well as anyequivalents.

While the present disclosure uses the term “small cell,” this term isused merely to illustrate the concepts herein, and nothing is impliedregarding size, power level etc. for any cells that could be used withthe disclosed systems and methods, i.e. “small cell” may be interpretedas including macro cells, femto cells, multi-radio access technology(RAT) access nodes, indoor cells, outdoor cells, etc.

Various alternative embodiments are also contemplated by the inventors.For example, certain functions may be performed at a multi-radio accesstechnology node (multi-RAT) node, instead of at a base stationmanagement gateway. The base station management gateway maysubstantially take the form of the described Parallel Wireless HetNetGateway. The base station management gateway may be a virtualizationserver. The functions of the base station management gateway may bebroken up and spread across multiple network nodes, or multiple softwareor hardware modules within the same network node, and may be physicallylocated in a single location, or multiple locations. The network nodemay be in the data path located between the radio access network (RAN)and the core network, in some embodiments, or may be located at anotherlocation in the network. A high-bandwidth wired connection may be usedfor backhaul, such as coaxial cable, fiber optic cable, or Ethernet, ora reduced-bandwidth wireless connection, such as microwave,line-of-sight, or other physical connections may be used as backhaul.

The protocols described herein may be optimized for greater or lesserlatency, for more or fewer mesh nodes, for more or fewer data streams,and other alternatives. In some embodiments, these optimizations may beperformed at the eNodeB, at the base station management gateway, withina function performing radio resource allocation and coding selection, orat another location. In some embodiments, a base station managementgateway may identify and initiate power adjustments to improve channelquality.

In some embodiments, the mesh network nodes may provide complete orpartial guesses at what paths are the optimal or best paths during aparticular time interval, and may be enabled to send messages back tothe base station management gateway to communicate these complete orpartial guesses.

In some embodiments, the base stations described herein may becompatible with a 3GPP UMTS or Long Term Evolution (LTE) radiotransmission protocol or air interface. The LTE-compatible base stationsmay be eNodeBs. In addition to supporting the 3G WCDMA protocol, thebase stations may also support other air interfaces, such as LTE,UMTS/HSPA, CDMA/CDMA2000, GSM/EDGE, GPRS, EVDO, other 3G/2G, legacy TDD,or other air interfaces used for mobile telephony. In some embodiments,the base stations described herein may support Wi-Fi air interfaces,which may include one of 802.11a/b/g/n/ac/ad/af/ah. In some embodiments,the base stations described herein may support 802.16 (WiMAX), or otherair interfaces. In some embodiments, the base stations described hereinmay provide access to land mobile radio (LMR)-associated radio frequencybands. In some embodiments, the base stations described herein may alsosupport more than one of the above radio frequency protocols, and mayalso support transmit power adjustments for some or all of the radiofrequency protocols supported.

The foregoing discussion discloses and describes merely exemplaryembodiments of the present invention. In some embodiments, softwarethat, when executed, causes a device to perform the methods describedherein may be stored on a computer-readable medium such as a computermemory storage device, a hard disk, a flash drive, an optical disc, orthe like. As will be understood by those skilled in the art, the presentinvention may be embodied in other specific forms without departing fromthe spirit or essential characteristics thereof. For example, wirelessnetwork topology can also apply to wired networks, optical networks, andthe like. The methods may apply to LTE-compatible networks, toUMTS-compatible networks, or to networks for additional protocols thatutilize radio frequency data transmission. Various components in thedevices described herein may be added, removed, or substituted withthose having the same or similar functionality. Various steps asdescribed in the figures and specification may be added or removed fromthe processes described herein, and the steps described may be performedin an alternative order, consistent with the spirit of the invention.Accordingly, the disclosure of the present invention is intended to beillustrative of, but not limiting of, the scope of the invention, whichis specified in the following claims.

The invention claimed is:
 1. A system, comprising: a base stationmanagement gateway situated between a multi-radio access technology(multi-RAT) radio access network (RAN), the multi-RAT RAN including bothof a 3G RAN and a non-3G RAN, and a packet core network and a circuitcore network, the base station management gateway providing resourcemanagement for a nodeB in the 3G RAN and the base station managementgateway providing routing and node management for a base station oraccess point in the non-3G RAN, wherein the base station managementgateway is configured to provide radio resource control, power control,ciphering, and multiplexing of multiple users onto a transmission pathfor a first 3G mobile device attached to the nodeB; wherein the basestation management gateway is configured to relay traffic for a secondmobile device attached to the base station or access point; and whereinthe base station management gateway is configured to relay traffic tothe circuit core network from both the nodeB and the non-3G RAN via anIuCS interface, and configured to relay traffic to the packet corenetwork from both the nodeB and the non-3G RAN.
 2. The system of claim1, wherein the base station management gateway is configured to interactwith the 3G RAN as a Radio Network Controller (RNC) and with the basestation as a home nodeB gateway (HNBGW).
 3. The system of claim 1,wherein the base station management gateway is configured to receivepackets from the nodeB and the base station, and to direct the receivedpackets to either an IuCS interface toward the core network or an IuPScore network interface toward the core network.
 4. The system of claim1, wherein the base station management gateway is configured to use anodeB application part (NBAP) protocol, an access link controlapplication protocol (ALCAP) protocol, a radio access networkapplication part (RANAP) protocol, and a radio network subsystemapplication part (RNSAP) protocol.
 5. The system of claim 1, wherein thebase station management gateway is configured to receive Iub protocolmessages from a 3G base station and Iuh protocol messages from a homenodeB.
 6. The system of claim 1, wherein the base station managementgateway is configured to terminate an encrypted connection with a 3Gmobile device, thereby providing a secure anchor point for the 3G mobiledevice for connection to the core network.
 7. The system of claim 1,wherein the base station management gateway is configured to terminateencrypted tunnels from the core network, from the first mobile deviceand second mobile device, and from the base station, and wherein thebase station is a home nodeB, and wherein the encrypted tunnels areInternet Protocol security (IPsec) or General Packet Radio ServiceTunneling Protocol (GTP) tunnels.
 8. The system of claim 1, wherein thebase station management gateway is configured to coordinate with asecond base station management gateway using an Iur protocol.
 9. Thesystem of claim 1, wherein the base station management gateway isconfigured to be aggregated with a second base station managementgateway via an interposing Iur protocol gateway.
 10. The system of claim1, wherein the base station management gateway is a virtualizationgateway providing virtualization of a plurality of home nodeBs towardthe core network.
 11. The system of claim 1, wherein the base stationmanagement gateway is configured to suppress paging messages for managedbase stations.
 12. The system of claim 1, wherein the base stationmanagement gateway is configured to perform inter-radio accesstechnology steering of a session from a first radio access technology(RAT) to a second RAT, the first RAT being one of 2G, 3G, 4G, andwireless local area networking (WLAN).
 13. The system of claim 1,wherein the base station management gateway is configured to provide oneor more application-aware inter-radio access technology (inter-RAT)slices across 3G, 4G, and wireless local area networking (WLAN)technologies, the inter-RAT slices being based on application-layerinformation gathered at the base station management gateway.
 14. Thesystem of claim 1, wherein the base station management gateway isconfigured to present itself toward the core network as a virtual radionetwork controller (VRNC).
 15. The system of claim 1, wherein the corenetwork is a 3G Universal Mobile Telecommunications System (UMTS) corenetwork comprising a mobile switching center (MSC) and a serving generalpacket radio service support node (SGSN).
 16. The system of claim 1,wherein the base station management gateway is configured to providehandovers between the nodeB and the base station using an Iub interfacewith the nodeB and an Iuh interface, an Iur interface, an Iurhinterface, or an 51 interface with the base station.
 17. The system ofclaim 1, wherein the base station is a multi-radio access network(multi-RAT) base station providing two or more of 2G, 3G, 4G, andwireless local area network (wireless LAN) radio access technologies.18. The system of claim 1, wherein the base station management gatewayis configured to provide handovers between the nodeB and one or more ofa 2G base station, a 4G base station, and a Wi-Fi access point.
 19. Asystem, comprising: base station management gateway means situatedbetween a 3G radio access network (RAN) and a core network, the basestation management means providing resource management for a nodeB andthe base station management means providing routing and node managementfor a base station, the core network including a circuit core networkand a packet core network, wherein the base station management means isconfigured to provide radio resource control, power control, ciphering,and multiplexing of multiple users onto a transmission path for a firstmobile device attached to the nodeB; wherein the base station managementmeans is configured to relay traffic for a second mobile device attachedto the base station; and wherein the base station management means isconfigured to relay traffic to the circuit core network from both thenodeB and the base station via an IuCS interface and configured to relaytraffic to the packet core network from both the nodeB and the basestation via an IuPS interface.